RFID skier monitoring systems and methods

ABSTRACT

A system and method monitor skier behavior. An identifier is read from a lift access product when the lift access product is in the vicinity of a lift boarding area and a scan record containing the identifier, location information of the lift boarding area and a time stamp if generated. The scan record is processed to generate a location event record that is stored within a location database. The location database is processed to determine skier behavior based upon the location event records.

RELATED APPLICATIONS

This application claims priority to U.S. Provisional Application Ser.No. 60/908,993, filed Mar. 30, 2007 and incorporated herein byreference. This application is also a continuation of (and claimspriority to) U.S. patent application Ser. No. 12/060,132, filed on Mar.31, 2008, entitled “RFID Skier Monitoring Systems And Methods,” which isincorporated herein by reference. This application is also related toU.S. patent application Ser. No. 14/161,524, entitled “System And MethodFor Tracking Activities Of A Customer At A Resort Area,” and U.S. patentapplication Ser. No. 14/161,532, entitled “System And Method ForAutomated Identification Of A Photographed Subject At A Resort Area”,filed on the same day as the present application, (Jan. 22, 2014), andwhich are incorporated herein by reference.

BACKGROUND

Traditional ski lift passes include a machine readable bar code thatallows authentication of the lift pass using a remote hand-held scanner.Such authentication is performed only at lower ski lift boarding areasthat are easily accessible by skiers; higher ski lift boarding beingattainable only after utilizing the lower ski lift.

Other lift pass authentication systems utilizes RFID tags to controlaccess at a turn-style, wherein an RFID scanner reads an RFID tag at ashort range, typically between 0.5 and 2 feet (0.1524 and 0.6096 meter),and limits access to ski lifts, by control of the turn-style, to validRFID tag holders.

SUMMARY OF THE INVENTION

In a unique approach to authenticating ski lift passes/tickets anddetermining customer ‘presence’ at ski lift boarding zones, customersare issued RFID-enabled ski lift access products (i.e., lift ticketsand/or season passes) that may be scanned manually at ski resort baseareas using handheld RFID scanners and scanned automatically at one ormore ski lift boarding areas using strategically mounted overhead RFIDscanners. Unlike other systems that require close proximity to operate,RFID scanning may occur at a range of 1-10 feet (3.048 meters) therebyallowing the ski lift access products to be read as customers of the skiarea (i.e., patrons of the ski resort) board the ski lifts. Theinformation gathered by these strategically placed RFID scanners formsthe basis for distinctive insight into crowd behavior at the ski areaand allows guest profiling to be conducted for purposes of marketing,resort operation, and guest servicing.

In an embodiment, an RFID skier monitoring system includes: a liftaccess product for each customer of a ski resort, the lift accessproduct having a unique identifier; at least one RFID scanner located ata boarding location of one or more ski lifts, the at least one RFIDscanner reading the unique identifier of each lift access product ascustomers board the one or more ski lifts, the at least one RFID scannergenerating a scan record comprising the unique identifier, a scanner IDand a time stamp for each unique identifier read; a location eventgenerator for generating a location event record for each scan record; alocation database for storing the location event record; and a serviceapplication for processing the location database to determine a profileof a skier using the lift access product.

In another embodiment, a method monitors skier behavior. An identifieris read from a lift access product when the lift access product iswithin a lift boarding area. A scan record containing the identifier,location information of the lift boarding area and a time stamp isgenerated. The scan record is processed to generate a location eventrecord which is stored within a location database. The location databaseis processed to determine skier behavior based upon the location eventrecord.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 shows one exemplary RFID skier monitoring system.

FIG. 2 is a schematic showing the system of FIG. 1 deployed at anexemplary ski resort.

FIG. 3 shows four exemplary location event records for a customeridentifier of “124365”.

FIG. 4 shows one exemplary RFID skier monitoring system configured withthree servers.

FIG. 5 shows a services application of the system of FIG. 1.

FIG. 6 shows exemplary tools of the service application of FIG. 1.

FIG. 7 shows one exemplary lift access product including a UHF RFID tag,an HF RFID tag, and a barcode.

FIG. 8 is a flow diagram illustrating exemplary operation of a hand-held(HH) RFID scanner reading a lift access product.

FIG. 9 shows successful pairing of scan records from an HH RFID scannerand a lift boarding area RFID scanner reading the same lift accessproduct.

FIG. 10 shows grouping of four close-together HH RFID scanner scanrecords of the same lift access product into a single transaction.

FIG. 11 shows successful pairing of two scan records read from the samelift access product by a boarding area RFID scanner and an HH RFIDscanner.

FIG. 12 shows one exemplary missed scan by a boarding area RFID scannerafter a lift access product is read by an associated HH RFID scanner.

FIG. 13 shows two successfully matched scan records from a boarding areaRFID scanner and an HH RFID scanner followed by a second scan recordfrom the boarding area RFID scanner with no matching scan record fromthe HH RFID scanner.

FIG. 14 shows a successful pairing of two scan records from an HH RFIDscanner and a boarding area RFID scanner followed by a duplicate scanevent from the boarding area RFID scanner.

FIG. 15 is a flowchart illustrating one exemplary customer profilingprocess, in an embodiment.

FIG. 16 is a flowchart illustrating one exemplary process for modelingcrowd behavior, in an embodiment.

FIG. 17 is a flowchart illustrating one exemplary process for deliveringon-slope messages, in an embodiment.

FIG. 18 is a flowchart illustrating one exemplary process for displayingskier activity, in an embodiment.

FIG. 19 is a flowchart illustrating one exemplary process for displayingski lift line wait times, in an embodiment.

FIG. 20 is a schematic illustrating one exemplary ski lift line and skilift wait time display.

DETAILED DESCRIPTION OF THE FIGURES

Information Gathering

A ski resort utilizes lift access products to control access to skilifts and, optionally, other facilities at the resort. These lift accessproducts may be divided into at least two classes: a first class liftaccess product (e.g., season passes), which has descriptive information(e.g., personal information of the lift product holder) associatedtherewith; and a second class lift access product (e.g., free sell lifttickets) does not include such associated information. The descriptive(personal) information associated with the first class lift accessproduct may include a photograph, and/or demographic information such asgender, birthday, and zip code of the lift access product holder. Thefirst class lift access product holder is thus a known and registeredcustomer of the resort. The second class list access product is notinitially associated with “a customer”.

Each lift access product (all classes) is affiliated with a uniqueidentifier that may be scanned at a time of authentication (e.g., at thebottom of the mountain prior when entering a ski lift line), or at atime of presence monitoring (e.g., while boarding a ski lift). Datagathered at the time of authentication and/or presence monitoringincludes the unique identifier of the lift access product, locationinformation of the authentication and/or presence monitoring, and adate/time stamp that indicates the time of the authentication and/orpresence monitoring.

In an embodiment, each lift access product may require activation at akiosk or other resort activation point, prior to use for that day. In analternate embodiment, each lift access product is automaticallyactivated upon first use at the resort.

FIG. 1 shows one exemplary RFID skier monitoring system 100. System 100is shown with a computer 102 in communication with two RFID scanners 104and 104(P). Although system 100 is shown with two RFID scanners 104 forclarity of illustration, system 100 may include more or fewer RFIDscanners without departing from the scope hereof. Computer 102 has a rawRFID database 106, a scan recorder 108, a location event generator 110,a location database 112 and a services application 118. Each RFIDscanner 104 includes a unique scanner identifier 124 and a real timeclock (RTC) 126 that maintains real time within RFID scanner 104. RTC126 is synchronized with an RTC 103 within computer 102. A lift accessproduct 120 has a unique identifier 122 that may be read by RFID scanner104 when lift access product 120 is in range of RFID scanner 104. Thatis, identifier 122 is stored within an RFID tag that is readable by RFIDscanner 104. Lift access product 120 is shown in further detail in FIG.7, and may comprise a high frequency (HF) RFID tag 706, an ultra highfrequency (UHF) RFID tag 702 and a bar code 720. HF RFID tags arepreferred for memory and security features, and UHF RFID tags arepreferred for their operational range. Thus, by including both HF andUHF RFID tags within lift access product 120, superior functionality canbe obtained over instances when only one or the other RFID tag type isused. Accordingly, RFID scanner 104 may include a HF RFID tag scannerand an UHF RFID tag scanner. As described with respect to FIG. 7, liftaccess product 120 may also include a barcode, thereby making liftaccess product 120 compatible with a range of scanning devices typicallyused within ski resorts. Hereinafter, the term RFID tag may refer to oneor both of the HF RFID tag and the UHF RFID tag.

In one example of operation, as lift access product 120 comes withinreading range of RFID scanner 104, RFID scanner 104 reads identifier 122and creates a scan record 128 that includes an identifier (e.g.,identifier 122), a scanner identifier (e.g., scanner identifier 124),and a time stamp based upon RTC 126. Scan record 128 is sent to computer102 via data path 130. In one example, scan record 128 is transmitted tocomputer 102 as soon as it is generated by RFID scanner 104. In anotherexample, RFID scanner 104 sends generated scan records (e.g., scanrecord 128) to computer 102 in batches, where a batch is sent everysixty seconds and contains scan records generated during that sixtysecond period. Data path 130 may include one or more wireless, optical,and wired connections. Scan record 128 is received by scan recorder 108and stored within raw RFID database 106.

In an embodiment, scan recorder 108 sends scan record 128 to locationevent generator 110 for further processing. In another embodiment, scanrecorder 108 notifies location event generator 110 of the arrival ofscan record 128 and location event generator 110 retrieves scan record128 from raw RFID database 106. In another embodiment, location eventgenerator 110 periodically scans raw RFID database 106 for unprocessedscan records. Location event generator 110 processes scan record 128 togenerate a location event record 132, based upon scanner locationinformation 114 and customer information 116, and stores location eventrecord 132 in location database 112. Location event record 132 includescustomer identification, location information and a time stamp for thatlocation event. For example, location event generator 110 matchesscanner identifier 124 of scan record 128 with a scanner location recordwithin scanner location information 114 to determine a location oflocation event record 132; location event generator 110 matchesidentifier 122 of scan record 128 with customer information 116 toassociate location event record 132 with a registered customer. Thus,location database 112 contains location event records (e.g., locationevent record 132) that define a recorded occurrence of lift accessproduct 120 near the location of RFID scanner 104. System 100 typicallyincludes many RFID scanners 104 (see for example FIG. 2), and thereforecan track movement of customers based upon locations of RFID scanners104.

By locating RFID scanner 104 at a ski lift (e.g., at the ski liftloading point), system 100 may identify customers using the ski lift byscanning their lift access products to read the associated identifier122.

FIG. 2 is a schematic of system 100 deployed at an exemplary ski resort200 that has three ski lifts 202, 208, and 214, each having an RFIDscanner 104(1), 104(2), and 104(3) located at a loading point 204, 210,and 216 of the ski lift, respectively. Ski resort 200 may have more offewer ski lifts without departing from the scope hereof. From a droppoint 206 of lift 202, two trails 220 and 222 are accessible; from adrop point 212 of lift 208, three trails 224, 226, and 228 areaccessible; and from a drop point 218 of lift 214, two trails 230 and232 are accessible. Each lift may access more or fewer trails withoutdeparting from the scope hereof. Since RFID scanners 104 are mounted tolift structures, base area grooming (i.e., the preparation of the snowby a snow cat or other similar devices) practices are unaffected.

FIG. 3 shows four exemplary location event records 132(1)-132(4)selected by services application 118 as identified by a customeridentifier “124365” for the 23^(rd) day of January, 2008. For example, auser may use a terminal 142 (e.g., a web browser running on a personalcomputer, a resort on-slope kiosk (e.g., kiosk associated with RFIDscanner 104(6), FIG. 2), etc.) to interact with services application 118via a web portal 140 and request services application 118 to querylocation database 112 and retrieve all location event records associatedwith customer identifier “124365” (e.g., the customer number of theuser). In the example of FIG. 3, location event record 132(1) indicatesthat customer 124365 boarded ski lift 208 at time 10:22:43 on Jan. 23,2008; location event record 132(2) indicates that customer 124365boarded ski lift 202 at time 10:38:01; location event record 132(3)indicated that customer 124365 boarded ski lift 208 at time 10:49:27;and location event record 132(4) indicated that customer 124365 boardedski lift 214 at 12:24:55. System 100 stores location event records 132for each customer carrying a lift access product (e.g., lift accessproduct 120); FIG. 3 shows location event records 132(1)-132(4) forcustomer number “124365.”

Scanner location information 114 may include additional information, foreach location, such as: trails (and levels) accessible directly from thelocation; trails (and levels) providing access to the location; resortzone(s) serviced by the location; vertical feet that the lift at thelocation ascends; other characteristics such as terrain types (e.g.,mogul/bump runs, groomed runs, tree skiing, bowl skiing, terrain park,etc.) accessible from the location; and distance from each base portal(e.g., ski area entry point). Thus, in the example of FIG. 2, locationof RFID scanner 104(1) may be associated by scanner location information114 with drop point 206, trails 220 and 222, and lift 208. Similarly,location of RFID scanner 104(2) may be associated with drop point 212,trails 224, 226, and 228, and ski lifts 202 and 214. Similarly again,location of RFID scanner 104(3) may be associated with drop point 218,trails 230 and 232, and ski lift 208. As RFID scanners 104 scan liftaccess products 120, scan records are sent to computer 102 forprocessing as described above.

Other information may be collected by computer 102 and processed togenerate location event records. As shown in FIG. 1, an access point 150has an RFID scanner 104(P) configured with a scanner identifier 124(P),a RTC 126(P) and application software 127(P). Access point 150 mayrepresent one of a point of sale (POS) system, a parking access system,a room key system, vending machines, member clubs, ski lockers, spa andpool areas, etc.

Where access point 150 is a POS system, RFID scanner 104(P) may readidentifier 122 of lift access product 120 to perform a financialtransaction. Lift access product 120 may operate as a contact-lesspayment card for use at POS systems within the resort, where the POSsystem identifies the customer based upon identifier 122, therebytransacting money with the customer's resort account. Lift accessproduct 120 may also operate as a stored value card and used for paymentat access point 150 (i.e., at a POS within the resort), wherein afinancial balance and transaction identifiers may be written to the RFIDtag. Access point 150 may then generate and send, via data path 154, atransaction record 158 to computer 102 for storage within a transactiondatabase 156. Data path 154 is for example an 802.11a WiFi networkoperating to provide connectivity between access point 150 and computer102. Other kinds of connectivity may be used without departing from thescope hereof. The financial balance of lift access product 120 may beincreased at kiosks throughout the resort through a credit cardtransaction for example.

In an embodiment, RFID scanner 104(P) generates and sends a scan record128(P) to scan recorder 108 for further processing. In an alternateembodiment, location event generator 110 processes information oftransaction database 156 to generate location event records 132 forstorage within location database 112 based upon POS transactions storedtherein. For example, a correlation between a customer ID used for POStransactions (i.e., stored within transaction database 156) andidentifier 122 of lift access product 120 may be stored within customerinformation 116. Further, even when identifier 122 is not scanned for aPOS transaction, information within customer information 116 may allowgeneration of location event record 132 based upon other transactedinformation.

Where access point 150 controls access to a parking garage, RFID scanner104(P) may control operation of one or more automatic barriers toprevent unauthorized use of the parking garage. Upon access to theparking garage, access point 150 and/or RFID scanner 104(P) may generateand send one or more of scan record 128(P) and location event record 132to computer 102 where an appropriate location event record 132 isgenerated and stored.

Where access point 150 controls access to a room, RFID scanner 104(P)may operate to unlock a door to the room based upon reading identifier122 of lift access product 120. As appreciated, operating range of theassociated RFID scanner may be selected to provide the appropriatecontrol. Access point 150 and/or RFID scanner 104(P) may generate andsend one or more of scan record 128(P) and location event record 132 tocomputer 102 where an appropriate location event record 132 is generatedand stored.

Computer 102 may include other databases for storing informationgathered by the ski resort. For example, computer 102 may store one ormore of weather conditions, snow conditions, grooming conditions, andthe terrain open to the public.

Authentication Kiosk

Access point 150 may also represent a self-serve kiosk 160 forauthenticating lift access products. Kiosk 160 may be located away fromlift lines and ticket sales to avoid congestion. System 100 may beconfigured with many kiosks 160 that are strategically locatedthroughout the ski resort. Kiosks 160 may be deployed at commongathering locations such as the top and bottoms of lifts. Customers mayuse kiosk 160 to check their ski area account, view their statistics andcheck for any personalized messages they might have received frommembers of their party or from the resort.

In operation, as a customer approaches kiosk 160, kiosk 160automatically detects the customer's lift access product 120. Theoperational range of the RFID scanner associated with kiosk 160 may beselected to provide optimal usability of kiosk 160 by customers. Kiosk160 may then display any services (e.g., group, messages, etc.) forattention of the customer. The customer may then log in to the kiosk(for example by using lift access product 120 at short range—1 inch(2.54 centimeters)—of the associated RFID scanner of kiosk 160). Thatis, the UHF RFID tag of the customer's lift access product 120 may bedetected at a range of 10 feet (3.048 meters), but login only occursupon close proximity scanning of the lift access product's HF RFID tag.

Upon log in, kiosk 160 may display the customer's name and home pagethat shows a summary of the customer's on-slope statistics, messages andthe last known location of other members of the customer's group, if thecustomer is associated with a group.

In an exemplary embodiment, kiosk 160 may include the followingfunctionality:

Display of General Statistics

When no customer is within RFID scan range of the kiosk, the kioskdisplays general statistics about the associated lift, such as averagelift ascent time and average descent time of skiers and boarders usingthe lift, and may display other on-slope statistics, such as averagewait times at on-mountain restaurants.

Automatic Detection

Kiosk 160 detects a customer (by scanning the customer's lift accessproduct 120) from a short distance away and automatically displaysmessages (or an indication of at least one new message) intended forthat customer. Where multiple customers are detected, messages may bedisplayed concurrently, or in turn, for each detected customer.

Display of Name and Statistics

After a customer is detected and logs in using their lift access product120 at close proximity, kiosk 160 displays the customer's name and showsthe customer's personal statistics, messages, and location of friends.The displayed statistics may include number of runs today, numbervertical feet today, average lift time, average descent time, and mostrecent descent time. Additional features may be added to post statisticsto certain Internet websites. Kiosk 160 may also display customerloyalty points that may be redeemed for gifts and services.

Pass Activation

When customers first arrive at the ski resort for the day (or theseason), the customer may activate their lift access product 120 atkiosk 160 without having to check in at a ticket counter. Kiosk 160 mayalso include a biometric reader/scanner to verify the customer'sidentity, as such the customer may need to remove one or more items ofclothing, such as a glove for fingerprint scanning, glasses/goggles foriris scanning, etc. Once verified, the lift access product is activatedfor use for the day (or optionally the season if so determined by theski resort operators).

Contact with Friends

A customer may look up friends that are in his/her group and find outthe most recent location and time they were recorded by system 100. Forexample, the customer may select a particular friend from their groupdisplayed at kiosk 160, whereupon kiosk 160 may show a particular skilift the friend is currently riding, or may show a time and lift lastridden by the friend. The customer may add one or more friends to theirgroup when these friends are also identified by (i.e., when thesefriends are within RFID scan range of) kiosk 160. In one example ofoperation, kiosk 160 detects a friend's lift access product 120 anddisplays the friend's thumbnail picture and name, thereby allowing thecustomer to add this friend to the group by simple selection.

Send Messages

A customer, once logged into kiosk 160, may select a friend in thecustomer's group and send a text message to that friend by typing themessage at the kiosk. The message is then stored until delivered to thefriend, when the friend is detected as proximate to, a message displayboard and/or a kiosk. Customers may also provide feedback to the resortby entering the message at kiosk 160.

Read Messages

Customers may read messages sent to them by friends and/or the resort.By approaching kiosk 160, the customer sees an indication (e.g., acount) of waiting messages. The customer may then login to the kiosk(i.e., by approaching closely) and retrieve messages. The resort maycommunicate with the customer, such as with regular updates on thestatus of a child in day care, and/or weather and traffic reports, if sorequested by the customer (e.g., by specifying message types fordelivery within a customer profile during online account interactionand/or kiosk interaction. These messages may include context sensitivemessages (e.g., messages based upon the customer's current location) andspecial offers, such as recommending runs commensurate with the type ofruns that skier has used in the past, and/or offering discounts at thenearest bar and/or restaurant.

Redemption of Awards

Kiosk 160 may have an awards screen where users may redeem earnedloyalty points for goods and/or services. Upon selection of a rewardand/or goods, kiosk 160 may credit the customer's account and/or printout coupons. For example, rewards could include a free massage at thespa, or a discount at a restaurant. Kiosk 160 may also allow customersto enter competitions, such as for the most vertical feet skied for theday (which may provide an incentive to avoid heavily trafficked runswhich could help load balance skiing traffic over the ski area) andprovide statistics as to customer's current status/rank in thecompetitions.

Automatic Logout

When the customer leaves proximity of kiosk 160, kiosk 160 loses contactwith the customer's lift access product 120 and the user isautomatically logged out. Alternatively, a customer may interactivelylogout of kiosk 160 by pressing a button. Kiosk 160 may indicate logoutby displaying a logout screen, or by switching back to a generalinformation display screen.

Distributed Functionality

FIG. 4 shows one exemplary RFID skier monitoring system 400 comprisingthree servers. That is, functionality of computer 102 is provided bythree communicatively connected and cooperating servers: a lift datacollection (LDC) server 402, a resort POS server 404, and a locationserver 406. The use of servers 402, 404, and 406 may facilitatedeployment of system 100 within a ski resort.

LDC server 402 operates to collect, store, and process raw RFIDinformation, such as scan record 128.

In particular, as shown in system 400, HH RFID scanners 420 need notconnect to the same server as RFID scanners 104.

Guest Benefits

The use of RFID tags allows lift access product 120 to be scannedthrough clothing, thereby not requiring the customer to present themedia for scanning. Since media presentation often entails removinggloves and opening jackets, the customer is less inconvenienced.

FIG. 5 shows location server 406 of FIG. 4 in further detail. A guesttracking service within services application 118 utilizes location eventrecords 132 within location database 112 to provide tracking informationto other members of grouped guests. A group 514 may be formed byassociating identifiers 122 of each member of the group together. Forexample, if a first customer has an identifier 122(1), and three friendshave identifiers 122(2), 122(3), and 122(4), group 514 is formed withidentifiers 122(1), 122(2), 122(3), and 122(4), through associationwithin group association database 510. Group 514 may be formed throughuse of a web browser, an on-mountain kiosk, and/or resort guestservices. Services application 118 may store a unique group identifierof each formed group in association with each identifier 122 of membersof the group within group association database 510, thereby forming thegroup association. Group 514 may be identified by searching groupassociation database 510 for groups containing a given identifier 122.It is therefore not necessary for customers to identify groups throughuse of a unique identifier other than their own identifier 122. A guesttracking module 512 of services application 118 determines members ofgroup 514 based upon any one of identifiers 122(1), 122(2), 122(3), and122(4). Other methods of identifying and storing groups within adatabase may be used without departing from the scope hereof.

Once a group (e.g., group 514) is identified, guest tracking module 512may be invoked to search location database 112 and retrieve last knownlocations of each group member. In one example of operation, firstfamily member interacts with an on-slope kiosk to form a group of allfamily members. Upon interaction with the kiosk, the first family memberis identified. Selecting a ‘create new group’ option on the kiosk formsa new group comprising the first family member. Other family members maythen be added to the group by scanning their lift access products 120 atthe kiosk.

Customers may also associate a cell phone 148 with their lift accessproduct 120 through use of a kiosk, web browser, etc. Thus enablingcellular portal 146 to identify the customer should they call or textthe cell portal from that cell phone. Customers may then use cell phones(e.g., cell phone 148) to access information of system 100 via cellularportal 146 without the need to enter their identifier 122 number eachtime.

Continuing with the example, if the family members become separated, thefirst family member may request location information of associated groupmembers by texting a location request to cellular portal 146 from theircell phone (e.g., cell phone 148). Upon receipt of this text message viacellular portal 146, services application 118 may first determine theidentifier 122 of the customer associated with the sending cell phone(i.e., using the sending cell phone number) and then identify othermembers of the associated group (e.g., group 514). For each of theidentified members, services application 118 may utilize guest trackingmodule 512 to determine the last recorded location and time known forthat member. Services application 118 may then send one or more textmessages containing the latest location and time information for eachother member of the group to the requesting cellular phone.

In another example, one member of the family group utilizes an on-slopekiosk to request the latest recorded location and time of other groupmembers. The kiosk interacts with services application 118 and guesttracking module 512 to determine the latest recorded location eventrecords for the identified group members and then displays theassociated location and time information on the screen of the on-slopekiosk. Since the on-slope kiosk identifies the group by scanning thelift access product 120 of the interacting customer, the on-slope kioskprovides diverse operation without complicated input requirements fromthe customer.

On Mountain Messaging

Services application 118 also includes a message hander 522 that allowspersonal messages to be delivered to on-slope customers. For example,on-slope display boards may be used to deliver messages to customerswhen addressed customers are within viewing range of the display board.Where multiple customers are within range of the display board, messagesfor these detected customers may be displayed concurrently and/orscrolled across the display board.

FIG. 17 is a flowchart illustrating one exemplary process 1700 fordelivering on-slope messages. Process 1700 may be implemented withinmessage hander 522. In step 1702, process 1700 receives a messageaddressed to a customer. In one example of step 1702, message handler522 receives a message 529 from a first customer 525, using an on-slopekiosk 528, addressed to a second customer 527. In another example,message 529 is received from one of a cell phone (e.g., cell phone 148)and a web browser (e.g., web browser running on terminal 142). Firstcustomer 525, using on-slope kiosk 528, may select second customer 527and enters message 529 for display to second customer 527. Firstcustomer 525 may identify second customer 527 by one of the customer'sname, the customer nickname, and the customer's identifier number (i.e.,identifier 122). Alternatively, first customer 525 may identify secondcustomer 527 by selection the second customer from a list of customersdefined within the group of first customer 525.

In step 1704, process 1700 stores the message in a message database inassociation with the customer. In one example of step 1704, messagehandler 522 stores message 529 within message database 520 with anassociation to second customer 527. In step 1706, process 1700identifies the customer within viewable range of a display board. In oneexample of step 1706, an RFID scanner 526 is associated with an on-slopedisplay board 524 and operates to identify (i.e., scan) lift accessproducts 120 of customers within viewing range of display board 524. Assecond customer 527 approaches display board 524, RFID scanner 526 readsthe identifier 122 of second customer 527, creates a scan record 128which is sent to location event generator 110. Location event generator110 generates a new location event record 132 and stores location eventrecord 132 within location database 112. Message handler 522 processeslocation database 112 to identify new location records 132 that indicatethat second customer 527 is within viewing range of display board 524.In step 1718, process 1700 sends the message to the display board fordisplay to the customer. In one example of step 1708, message hander 522sends message 529 to display board 524 for display to second customer527. In step 1710, process 1700 increments a message display count forthe message. In one example of step 1710, message hander 522 incrementsa count associated with message 529 within message database 520. Step1712 is a decision. If, in step 1712, process 1700 determines that themessage has been viewed, process 1700 terminates; otherwise process 1700continues with step 1714. In step 1714, process 1700 deletes the messagefrom the message database. In one example of steps 1712 and 1714,message hander 522 maintains a count of the number of times each messageis displayed, and deleted the message after it has been displayed threetimes, thereby increasing the probability that the message has been readby the intended recipient.

In an embodiment, display board 524 is located at a ski lift base suchthat customer boarding the ski lift may read the display board and RFIDscanner 526 represents one of RFID scanners 104 that operate to identifycustomers boarding the ski lift.

In an alternate embodiment, upon receipt of message 529, message hander522 sends message 529 to display board 524 where it is stored locallyuntil displayed or until the defined valid period of the messageexpires. The message may include identifier 122 of the customer to whomit should be displayed. In this embodiment, RFID scanner 526 scansidentifier 122 of each customer within viewable range of display board524 and sends the scanned identifier 122 to display board 524. Uponreceiving the scanned identifier, display board 524 searches its localmemory to determine whether there are any messages for the identifiercustomer. Any messages associated with the identified customer aredisplayed on display board 524. Thus, after receiving messages fordisplay (e.g., message 529), display board 524 and RFID scanner 526operate independently of services application 118 and computer 102 todisplay messages to identified customers.

Skier Activity Portal

Services application 118 may also include skier activity module 532 thatallows a customer to view their activity at the ski resort. Skieractivity module 532 retrieves location event records 132 from locationdatabase 112 and processes them to determine customer activity for acustomer selected period.

Skier activity module 532 and web portal 140 cooperate to provide astatistics web site 534 where customers are able to access theirpersonal activity statistics based upon location event records 132captured during their activity at the resort. For example, customerswill be able to log in to the web site and review statistics of thenumber of days skied at each resort. For each day, the customer mayreview weather, snow, and grooming conditions, amount of vertical feetskied by mountain zone and mountain statistics, such as the total numberof skiers on mountain that day by mountain zone, the average verticalfeet skied by guests that day, broken down by mountain zone anddemographic. Customers may download their statistics and publish them totheir social networking web sites, for example. Customers may view atrail map of the ski resort populated with lifts ridden with date-timestamps and lift progression. The trail map may be interactive, allowingthe customer to identify and record the trails ridden from each lift,thereby allowing the customer to recreate their on-mountain experience.

FIG. 18 is a flowchart illustrating one exemplary process 1800 fordisplaying skier activity. Process 1800 is implemented within skieractivity module 532, for example. In step 1802, process 1800 identifiesthe customer and the activity period for analysis. In one example ofstep 1802, a customer logs into statistics web site 534 to viewstatistical information accumulated from a selected period of skiing.The log in process identifies the customer based upon one or more of auser name and password associated with identifier 122 of the customer'slift access product 120. The customer then selects a period based uponinformation recorded by system 100 for that customer. In another exampleof step 1802, as the customer approaches an on-slope kiosk (e.g., akiosk 240, FIG. 2), the kiosk automatically identifies the customer, andupon close scan of the customer's lift access product 120, logs thecustomer into statistics web site 534 and selects the current day as theactivity period.

In step 1804, process 1800 selects location event records for thecustomer identified in step 1804 and for a selected activity period. Inone example of step 1804, skier activity module 532 selects locationevent records 132 associated with the identified customer for theselected activity period. In step 1806, process 1800 generates a map ofthe ski resort identifying lifts ascended by the identified customerbased upon the selected location event records. In one example of step1806, skier activity module 532 identifies each lift ascended by thecustomer based upon location event records 132 resulting from scanrecords 128 captured at lift boarding areas (e.g., lift boarding area2004, FIG. 20). Skier activity module 532 then generates a map of theski resort and indicates lift boarding times of the customer at each skilift.

Steps 1808 through 1814 form a loop that repeats to allow the customerto interactively identify trails skied after ascending each lift. Steps1808 through 1814 repeat for each identified lift ascent, based uponselected location event records of step 1804. In step 1810, process 1800interacts with the customer to identify trails taken from the liftascent of step 1808. In one example of step 1808, skier activity module532 highlights the lift ascent of step 1808 on the displayed map andinteracts with the identified customer to select one or more trails thatare accessible from that lift ascent, based upon topology information250. In one embodiment, skier activity module 532 validates selectedtrails and highlights improbable selections (e.g., where a customer hasselected a trail that is not easily accessible from the specified lift).In step 1812, process 1800 stores the identified trails in associationwith the customer and the lift ascent of step 1808. In one example ofstep 1812, skier activity module 532 stores identified trails of step1810 within a skier activity database 538 in association with theidentified customer of step 1802 and the lift ascent of step 1808. Steps1808 through 1814 repeat for each lift ascent made by the identifiedcustomer for the selected activity period unless terminated by thecustomer.

In step 1816, process 1800 displays a map of the ski resort indicatinglift ascents and identified trails. In one example of step 1816, skieractivity module 532 displays a map of the ski resort, identifying skilifts ascended and identified trails, via web portal 140 and statisticsweb site 534. In step 1818, process 1800 displays activity statisticsfor the identified customer and selected activity period, including anumber of vertical feet skied during the selected period. In one exampleof step 1818, skier activity module 532 sums the vertical feet of eachlift ascent of step 1808 for display to the customer as a total verticalfeet skied statistic, counts the number of lift ascents for display as alifts ridden statistic, and determines a vertical feet per minuteaverage based upon the total vertical feet skied statistic and theselected activity period for display as a vertical feet per minutestatistic. Skier activity module 532 then displays these determinedstatistics to the customer via web portal 140 and statistics web site534.

Web portal 140 may also allow customers to “publish” their vertical feetstatistics to a competition web site 536 and optionally enter one ormore contests by resort, by zone, by demographic, and/or across multipleresorts. Thus, the customer may view their ranking versus their friends,family, and guests in similar demographics. Where the customer is partof a defined group (e.g., group 514), other members of that group mayaccess determined statistics of each member of the group. For example,these statistics may allow for friendly competitions and rankings forselected periods and for statistics for total vertical feet skied,number of days skied, resorts zones skied, multiple resort statistics,etc.

On-Slope Photographer Customer Tracking

Ski resorts often have on-slope photographers (sharpshooters) thatcapture images of customers in the hope that customers will buy theimages when they have finished skiing. Typically this requires that thecustomer visit a ski lodge or other location at the resort base toidentify and purchase the images from the photographer. Where thecustomer forgets to visit the photographer, the images are typicallyerased and the photographer earns no money.

By using an RFID scanner (e.g., RFID scanner 104) to identify thecustomer prior to and after images are captured of the customer, thephotographer may contact the customer through the resort contactinformation and/or web site. In one example, the photographer may emaillow resolution and/or watermarked images to the customer with a link toa web site operated by the photographer where the customer may purchasethe images. In another example, the photographer provides an indicationwithin the resort's web site such that the customer is notified of theavailable pictures upon logging into and/or connecting to the resort website.

In an embodiment, the photographer uses a handheld RFID scanner to readidentifier 122 of customers he has photographed. In another embodiment,an RFID scanner is position at a marked location on the slope to captureidentifiers 122 of potential customers. The photographer then capturesimages of customers passing through the marked location and associatedan image identifier with the captured identifier of the customer.

To enhance customer information, additional on-slope locations mayinclude RFID scanners to identify customers visiting those locationssuch that location event records may be stored of those visits. Forexample, terrain park features such as jumps, rails, half-pipes, mayinclude RFID scanners that read identifier 122 and generate scan recordsas a customer rides the terrain park feature. These scan records, aspreviously described, are used to generate location event records thatmay be processed to display one or more runs made by the customerthrough the terrain park. For example, the customer may access a webpage to view a detailed map of the terrain park where the customer's useof the features is marked with a date/time stamp and or feature useorder. In an embodiment, points may be assigned to each feature suchthat customers may accumulate points as a measure of feature usage. Suchinformation may then be shared, at the customer's discretion, acrosscustomer groups.

Mountain Operations

FIG. 6 shows exemplary tools of services application 118 as used by skiresort staff (e.g., mountain operation staff, marketing, etc.).

System Integrity and Performance Monitoring

Services application 118 includes an integrity tool 690 thatcontinually, and/or periodically, monitors operation and performance ofsystem 100. In the embodiment shown in FIG. 4, integrity tool 690 islocated within services application 118(1) of LDC server 402.

Integrity tool 690 processes scan records 128 of raw RFID database 106to monitor performance of hardware and software components of system100. Integrity tool 690 monitors scanning performance of each RFIDscanner 104 by processing information of each scan record 128. In anembodiment, scan record 128 also includes operational data such astemperature, memory utilization, communication reliability, etc.Integrity tool 690 processes this operational data to identify anyfailing and failed components of system 100. For example, wherecommunication reliability between RFID scanner 104 and computer 102becomes unreliable, integrity tool 690 may alert operators toinvestigate and repair one or more intermediate communication devicesand/or RFID scanners 104.

Integrity tool 690 may also identify anomalies in the scannedinformation that may be caused by component failure and/or poorconfiguration based upon location event records 132. In this case,integrity tool 690 may operate within services application 118(2) ofFIG. 4 and process location event records 132 of location database 112.

Integrity tool 690 utilizes several assumptions about customer boardingscenarios at each ski lift. Using the example of FIG. 2, RFID scanner104(1) scans lift access products 120 of skiers boarding ski lift 202and a hand-held (HH) RFID scanner 104(4) is also used to scan andvalidate lift access products 120 of skiers intending to board ski lift202. A first assumption is that, for a customer using ski lift 202, alocation event record 132 from RFID scanner 104(1) and a location eventrecord 132 from HH RFID scanner 104(4) may occur (and thus be receivedby computer 102) in any order. A second assumption is that multiple scanrecords 128 for the same lift access product 120 may occur for a singleboarding of a customer. A third assumption is that duplicate scanrecords from a lift boarding area RFID scanner (e.g., RFID scanner104(1)) are not desirable. If it takes fifteen minutes to board a lift,ride the lift to the top and ski down to the lift loading point, scanrecords for the same lift access product made by the RFID scanner at thelift boarding area within that time period are assumed to be duplicateand that the customer has not boarded the lift.

Thus, during normal operation, a scan record from a HH RFID scanner anda scan record from a boarding area RFID scanner occur close in time; theordering of the scan records being unimportant.

Expected timing of received scan records varies as the length of thelift line varies and the lift boarding process changes. Changes to thelift boarding dynamics impact HH RFID scanners and boarding area RFIDscanners differently.

In a first ‘busy ski lift’ scenario, a customer skies to the end of thelift line at ski lift 202 and their lift access product 120 is scannedby HH RFID scanner 104(4) as they enter the lift line. The customer thenspends a few minutes moving toward the front of the lift line and thenboards the ski lift where RFID scanner 104(1) scans their lift accessproduct 120. In this first scenario, it is likely that HH RFID scanner104(4) scans the customer's lift access product 120 several minutesbefore the same customer's lift access product 120 is scanned by RFIDscanner 104(1).

In a second ‘non-busy ski lift’ scenario, a customer skis up to ski lift202. Since there is no line for lift 202, HH RFID scanner 104(4) may belocated nearer the loading area of lift 202 that in the case of thefirst scenario. Thus, the customer's lift access product is scanned byboth HH RFID scanner 104(4) and RFID scanner 104(1) within a shortperiod of time; the ordering of scan records resulting from these scansis not determinate. Adding to this complexity, even when the ski lift isbusy, the behavior of Ski School and Singles lanes may be closer tobehavior of the non-busy scenario, since their use may be restricted tofewer customers having different activity schedules.

Three periods may be considered when modeling lift line behavior: Δt1,Δt2, and Δt3. Δt1 is the maximum time between a lift access product 120of a customer being scanned by RFID scanner 104(1) at the boarding areaof lift 202 and the lift access product being scanned by HH RFID scanner104(4) when lift 202 is not busy. Δt1 is defined as one minute, forexample. Δt2 is the maximum time between a lift access product 120 of acustomer being scanned by HH RFID scanner 104(4) and then being scannedby RFID scanner 104(1) at the boarding area of lift 202 when lift 202 isbusy. Δt2 is defined as ten minutes, for example. Δt3 is defined as theminimum time required for a customer to ride the lift to the top and skidown to the lift base. Δt3 is defined as fifteen minutes, for example.

FIG. 8 is a flow diagram illustrating exemplary operation of a HH RFIDscanner (e.g., HH RFID scanner 104(4), FIG. 2) to read lift accessproduct 120. An operator 802 pulls at step 810 a trigger on HH RFIDscanner 104(4) while aiming HH RFID scanner 104(4) at a customer's liftaccess product 120. HH RFID scanner 104(4) starts scanning at step 812for barcodes within range. If a barcode is read, a barcode is returned814; otherwise a null is retuned after a timeout period (e.g., 1 minute)of if the operator releases at step 818 the trigger. If a barcode isread, the identity may be displayed and transacted upon 816. Operator802 then releases at step 818 the trigger. At this point, the customerhas been identified by reading the barcode on the lift access product120.

If null is returned, indicating that no barcode was read, HH RFIDscanner 104(4) initiates at step 820 an RFID scanning process. In oneexample, the scanning process operates for 0.5 seconds and all readRFIDs are then evaluated. If no RFID tags were read, a null is returnedat step 822; otherwise a list of RFID tag identifiers are returned atstep 822. If a single RFID tag identifier is returned, HH RFID scanner104(4) displays and transacts at step 824 the identifier; if no or morethan one RFID tag identifier is returned an error is displayed at step824 requesting a re-read.

Thus, HH RFID scanner 104(4) may first try to scan the barcode and ifthat fails may try to read RFID tags of the lift access product. In oneembodiment, HH RFID scanner 104(4) operates to read both barcode andassociated RFID tags of each lift access product 120.

Once the lift access product 120 is identified, computer 102 may send animage and/or demographic information of the customer for display on ascreen of HH RFID scanner 104(4), thereby allowing the operator toverify that the customer is using their own lift access product 120.

FIG. 9 shows one exemplary scenario where HH RFID scanner 104(4) andlift boarding area RFID scanner 104(1) generate scan records from onelift access product 120. To consider both Busy and Not Busy scenarios, asuccess requires that the boarding area read event occurs less than Δt1before the HH RFID scanner read event and less than Δt2 after the HHRFID scanner read event. Multiple HH RFID scanner reads during a singlelift boarding are considered as a single read event to avoid anartificially high rate of hoarding area RFID scanner read events beingflagged as missed. That is, multiple HH RFID scanner read eventsoccurring in less than Δt2 may be grouped into a single transaction witha start time of the first HH RFID scanner read and an end time of thelast HH RFID scanner read, as shown in FIG. 10 where four close-togetherHH RFID scanner reads of the same lift access product 120 are groupedinto a single transaction. In this example, each of Δta, Δtb, and Δtcare each less than 1 minute.

FIG. 11 shows one scenario where a boarding area RFID scanner reads alift access product within Δt2 of a HH RFID scanner reading the liftaccess product.

FIG. 12 shows one scenario where a boarding area RFID scanner has missedreading a lift access product that was read by an associated HH RFIDscanner. A missed boarding area RFID scanner event occurs when an HHRFID scanner reads a lift access product, but there is no correspondingboarding area RFID scanner scan record within a period Δt1 before the HHRFID scanner read and a period Δt2 after the HH RFID scanner read.

Each customer boarding a base ski lift should be scanned by a HH RFIDscanner. In some cases, human error may result in a customer not beingscanned by a HH RFID scanner. Although not considered a failure ofsystem 100, statistics are collected and evaluated to avoid distortingthe data.

A missed HH RFID scanner read is considered to have occurred when eitherof the following two conditions are met: (a) a boarding area RFIDscanner read event occurs, and there is no corresponding HH RFID scannerread event within Δt1 before the boarding area RFID scanner read event,and within the period Δt2 after the boarding area RFID scanner readevent; and (b) the boarding area RFID scanner read event is notconsidered a duplicate event. See FIG. 13 which shows a successful matchof a boarding area RFID scanner read events and a HH RFID scanner readevent, followed by a missed HH RFID scanner read event.

The goal of each RFID scanner 104 located at a boarding area of a skilift is to generate a single RFID scanner read event for each customerboarding the ski lift. Thus, duplicate boarding area RFID scanner readevents for a customer boarding the ski lift constitutes a failure of theRFID scanner (and/or its supporting sub-system). When trying tocategorize a boarding area RFID scanner read event as a potentialduplicate, the following heuristic is used: since the minimum timerequired for a customer to ride the ski lift and ski back down to theboarding area is Δt3, if multiple boarding area RFID scanner read eventsfor a single customer occur in less than time period Δt3, they arepotential duplicates. In rare cases, a customer may be read by theboarding area RFID scanner, leave the lift line, and return to the liftline in less than the period Δt3. If this situation occurs, it isassumed that the lift access product of the customer will be read by anHH RFID scanner read again.

Duplicate boarding area RFID scanner read events are thus identifiedwhen two conditions are met: (a) multiple boarding area RFID scannerread events occur within Δt3; and (b) there are no interveningindividual HH RFID scanner reads for the same lift access productbetween the boarding area RFID scanner read events. Also of note, aduplicate boarding area RFID scanner read event is always accompanied byone of: (a) a successful match between a boarding area RFID scanner readevent and an HH RFID scanner read event; and (b) a missed HH RFIDscanner read. FIG. 14 shows a successful pairing of an HH RFID scannerread event and a boarding area RFID scanner read event followed by aduplicate boarding area RFID scanner read event.

Thus, the performance of system 100 may be determined by countingsuccessful parings of scanned events and counting failures. For example,integrity tool 690 may continually and/or periodically process scanrecords 128 of raw RFID database 106 to count these successes andfailures, thereby monitoring operation of system 100. In one example ofoperation, integrity tool 690 processes scan records 128 of raw RFIDdatabase 106 for each customer (i.e., each identifier 122) for a givenday. By identifying the number of successful paired scan records, andgrouping pairing failures, for each boarding area RFID scanner and HHRFID scanner, integrity tool 690 may identify components of system 100that have problems and may produce one or more reports of componentoperability status. Such reports may highlight areas for hardware and/oroperator and operating strategy improvements.

When performing the analysis of raw RFID database 106, integrity tool690 associates each scan record with only one success or failure. Forexample, integrity tool 690 may first identify all successful scanrecord pairings, and then identify failures in the remaining scanrecords to identify failed HH RFID scanner reads and duplicate HH RFIDscanner reads.

Since each HH RFID scanner (e.g., HH RFID scanner 104(4)) may include abarcode reader, the use of the barcode reader should also be noted sincethis may result in a higher level of missing HH RFID scanner reads thatactually occur. In one embodiment, integrity tool 690 may import barcodescan information for use in matching boarding area RFID scanner scanrecords. In an alternate embodiment, where barcode scanning by HH RFIDscanners may occur, HH RFID scanner read failures are ignored.

Each HH RFID scanner 104 may include a display such that upon scanningeach identifier 122, the HH RFID scanner receives an image, fromcomputer 102, of the customer associated with the scanned identifier 122(i.e., computer 102 returns an image of the customer associated with thelift access product 120 identified by the scanned identifier 122). Thus,the operator of the HH RFID scanner may verify that the user of theidentified lift access product 120 is the associated customer, toprevent fraudulent use of lift access product 120.

Computer 102 may also return other information to the HH RFID scanner,such as customer demographic information that may further identify theassociated customer and to allow for a highly customized customerexperience for high value guests; club member profiles that allow the HHRFID scanner operator to identify Club Members.

As shown in FIG. 6, services application 118 may include a customerprofiler module 610 that operates to process information of locationdatabase 112 and generate customer profile information for one or morecustomers. FIG. 15 is a flowchart illustrating one exemplary customerprofiling process 1500. Process 1500 is implemented within customerprofiler module 610, for example.

In step 1502, process 1500 selects an analysis period. In one example ofstep 1502, a default period of 24 hours, from 0000 through 2359 of thecurrent day, is selected. In another example, a user of system 100interacts with customer profiler module 610 to select a period includingseveral past days. In step 1504, process 1500 selects a customerdemographic profile for analysis. In one example of step 1504, the userinteracts with customer profiler module 610 to select all customerdemographic profile areas.

Steps 1506 through 1516 form a loop that is executed for each customeridentified by steps 1502 and 1504. In step 1506, process 1500 selectseach customer identified by steps 1502 and 1504 in turn. In step 1508,process 1500 selects location event records associated with ski liftboarding areas for the customer during the selected analysis period. Inone example of step 1508, customer profiler module 610 selects locationevent records 132 from location database 112 for the customer identifiedin step 1506 for the analysis period selected in step 1502. In step1510, process 1500 orders the selected location event recordschronologically. In one example of step 1510, customer profiler module610 sorts the selected location event records 132 of step 1508 intoascending chronological order. In step 1512, process 1500 determines thelift progression for the customer. In one example of step 1512, customerprofiler module 610 determines the sequence in which the customer boardsski lifts during the selected analysis period. In another example,customer profile module 610 determines a vertical feet profile basedupon the ski lifts used by the customer, and stores a vertical feet perday and/or a vertical feet per hour value. In step 1514, process 1500stores the determined lift progression sequence in the customer'sprofile. In one example of step 1514, customer profiler module 610stores the lift progression sequence in association with the customer ofstep 1506 within customer profile database 612. Steps 1506 through 1516repeat for each customer identified by steps 1502 and 1504.

Once location event records 132 have been processed for all customersidentified by steps 1502 and 1504, in step 1518, process 1500 analyzesthe determine lift progression sequences for all customers selected bysteps 1502 and 1504 to identify trends and behavior patterns for theselected customer demographic profile of step 1504. This profileinformation may then be used as described below.

Fraud Detection

By scanning lift access products 120 at each lift boarding area, theprobability of detection of fraudulent lift use increases as compared tocurrent techniques where lift tickets are scanned only at base lifts(i.e., lifts located at the base area of the resort). Each RFID scanner104 includes application software 127 that includes offline frauddetection algorithms that evaluate each scanned lift access product 120.As shown in FIG. 7, each lift access product 120 may include a UHF RFIDtag 702, an HF RFID tag 706 and a barcode 720. UHF RFID tag 702 mayinclude identifier 122 and a security seal 704; HF RFID tag 706 mayinclude identifier 122, a fraud score 708, a financial value 710, anoperational date 712 and a security seal 718. In an embodiment, eachidentifier 122(n) has a different barcode and RFID tag identifier foreach customer n.

In an embodiment, application software 127 evaluates security seal 704of UI IF RFID tag 702 and/or security seal 718 of HF RFID tag 706. Sincesecurity seals 704 and 718 are based upon content of each RFID tag 702,706, respectively, fraudulent tampering with tag contents may beidentified by application software 127. Furthermore, applicationsoftware 127 may compare operational date 712 against the date value ofRTC 126 to determine whether lift access product 120 is valid for thecurrent day. That is, RFID scanner 104 may determine validity of liftaccess product 120 offline. RFID scanner 104 may thus validate each liftaccess product 120 without necessarily communicating with computer 102.

Application software 127 may compare fraud score 708 of HF RFID tag 706with a threshold value to determine if fraudulent use of lift accessproduct 120 is suspected. If the value of fraud score 708 is greaterthan the threshold value, lift access product 120 may be flagged by RFIDscanner 104 for further evaluation.

Even though each lift access product 120 is evaluated at each scan, scanrecords 128 and location event records 132 may be further evaluated by afraud detector 660 within services application 118 of computer 102. Inparticular, fraud detector 660 processes location event records 132 oflocation database 112 to identify fraudulent use of lift passes. Frauddetector 660 may also utilize a product validity database 662 thatcontains lift access product validity information to further evaluatethe validity in use of each lift access product 120. For example,product validity database 662 may define one or more of an operationaldate range, a number of days purchased, and a number of days used.

Fraud detector 660 also processes location event records 132 of locationdatabase 112 to identify potentially fraudulent behavior associated witheach lift access product 120. Fraud detector 660 may process locationevents records associated with one lift access product 120 to comparecurrent behavior with previously recorded behavior. Where current andprevious behavior is dissimilar, fraud detector 660 may increment afraud counter associated with the lift access product 120. For example,where a skier has a history of skiing in a difficult terrain area andcurrently is skiing in a beginner area, fraud detector 660 increases thefraud score for each uncharacteristic run made.

In one embodiment, fraud detector 660 utilizes customer profiler module610 to profile one or more previous days skiing and to profile thecurrent day of skiing for each currently active lift access product(i.e., each lift access product recently detected). By comparingprevious and current profiles associated with each active lift accessproduct 120, fraud detector 660 may increment the fraud score associatedwith the lift access product if the profiles are dissimilar.

In another method of fraud detection, application software within eachRFID scanner 104 associated with a ski lift loading zone may count anddisplay the number of lift access products 120 boarding each chair.Thus, upon noticing a discrepancy with the displayed number and thenumber of actual people boarding, ski lift attendants may note thediscrepancy such that the issue may be resolved by manual scanning ofthese customers upon arrival at the top of the lift.

Fraud detector 660 may also track previous fraudulent use of a liftaccess product thereby modifying the fraud score 708 accordingly.

Application software 127 within RFID scanner 104 may increase fraudscore 708 of a lift access product 120 if one or both of security seals704 and 718 indicate tampering with one or both of RFID tags 702 and706. Where a customer is also renting equipment tagged with one or moreRFID tags, and one or more of these rental equipments tags changes, RFIDscanner 104 increases fraud score 708 of the associated lift accessproduct 120.

Fraud detector 660 may also increase a fraud score associated with alift access product 120 as time between the last attendant or biometriccheck elapses, thereby ensuring that each lift access product 120 isverified periodically. Fraud detector 660 may also increase a fraudscore associated with a lift access product 120 if the lift accessproduct is associated with a different group (e.g., group 514) of liftaccess products than usual. Fraud detector 660 may also increase a fraudscore associated with a lift access product 120 if a previously usedparking tag has not been used. Fraud detector 660 may also increase afraud score associated with a lift access product 120 if other programswith affinity to the lift access product are not used. Fraud detector660 may also increase a fraud score associated with a lift accessproduct 120 if the lift access product 120 is used of a different day ortime of week than previously recorded.

The fraud score associated with each lift access product 120 thusincreases as potentially fraudulent events or circumstances occur. Sincefraud score 708 may be evaluated each time the lift access product 120is scanned, fraudulent use of the lift access product 120 is morerapidly identified and more easily resolved. For example, upondetermining that fraud score 708 exceeds the threshold value, RFIDscanner 104 may indicate that the last scanned lift access product 120needs further evaluation. This indication typically occurs as liftaccess product 120, carried by a customer, enters a ski lift line,and/or boarding area, and is identified by the RFID scanner 104 thereat.In such a case, the attendant may ask the customer for proof of identity(e.g., by matching a fingerprint or verifying the picture, height, etc.,of the customer associated with the lift access product 120). Uponsuccessful proof of identity, the associated fraud score 708 may bereset and the customer is allowed to continue without interruption (atleast until their fraud score exceeds the threshold again).

Last Scanned Location for Search and Rescue

When a customer is reported lost, resort safety personnel may utilize asearch module 602 within services application 118 of system 100 todetermine a last scanned location of the customer's lift access product120 by searching for the associated identifier 122 within locationdatabase 112. Upon determining the last know location of the customer,the resort safety personnel may better focus the search to areas nearerto that last known location, thereby positively impacting the time torescue.

Staff Tracking

Typically, a sign-in and sign-out method is used to ensure all staffreturn from on-slope operations at a ski resort at the close of day.However, when using this sign-in/sign-out method, if a staff memberfails to sign-out, an on-slope search process is usually initiated forsafety reasons. By issuing each employee of the resort with a liftaccess product 120, operations staff may improve safety of on-slopestaff by tracking staff movements on and off the slope. In anembodiment, a staff tracking module 604 within services application 118may automatically operate to ensure all staff going on-slope, return.For example, staff tracking module 604 may include intelligentalgorithms that monitor staff movements and raise an alert whenunexpected behavior or situations (e.g., a staff member failing toreturn from an on-slope activity).

Furthermore, when an alert situation is determined, staff trackingmodule 604 may provide a movement history of the missing staff member toenable faster rescue and/or resolution of the alert. In an embodiment,system 100 may include RFID scanners (e.g., RFID scanner 104) withinstaff accessible locations and commonly accessed areas to improve stafftracking and thereby increase staff safety.

Customer Profiling

Customer profiler module 610 may utilize information stored withincustomer information 116 and stored location event records 132 withinlocation database 112 to determine and categorize an activity level ofthe customer. Customer profiler module 610 may then store this customerprofile information within customer profile database 612 in relation tocustomer information 116 and the customer's identifier 122.

As described above, customer profiler module 610 may determine thevertical feet per hour skied by each customer, and store the verticalfeet per hour value as a measure of skiing intensity. Skiing intensitymay be further analyzed by determining the duration for which theintensity level is maintained. For example, one customer may ski hardfor one hour and then take a break before skiing hard again, whereasanother customer may ski hard for the entire day. Further, customerprofiler module 610 may determine customer ski lift riding patterns andthereby associate probabilities for these patterns based upon customersegmentation, product segmentation, time of year, day of week, weatherconditions, and customer volume at each lift and/or at the resort. Forexample, certain customers may prefer to ski where lifts and trails areless crowded. By monitoring these determined behavioral patterns,strategic placement of new lifts and prioritization of lift upgrades maybe determined.

Customers may be categorized by age group, gender, and otherdemographics. The determined customer profile (as stored within customerprofile database 612) may thus be applied with these categorizations topredict behavior of customers at the resort. customer profiler module610 may also analyze lift progression of each customer, to formstatistical information on lift riding patterns by customers of eachdemographic and profile. Such information may be used by a liftprogression model 632, as described below.

Services application 118 may include a modeling tool 630 that modelscustomer behavior based upon customer profiles and measured on-slopecharacteristics. Modeling tool 630 may be used to predict when and wherelarge customer numbers (i.e., crowds) will occur, thereby allowingoperation of the mountain to be adjusted to optimize mountain staffdispatch, grooming priorities, messaging in on-slope displays, and snowmaking priorities. For example, if historical data indicates thatcertain weather conditions and customer demographics result in heavy useof certain lifts, additional staff may be dispatched to that lift inpreparation of the crowds and on-slope displays may suggest use ofalternate areas to avoid overcrowding of those lifts.

Modeling tool 630 may utilize or incorporate lift progression model 632to model lift riding patterns of customers based upon their customerprofile and/or demographic. Modeling tool 630 may thereby predictcustomer on-slope movements to model crowd behavior for predictivemanagement purposes. For example, modeling tool 630 may display a trailmap with predicted crowd behavior for a selected time based uponhistoric information, profiled behavior and predicted and/or measuredcustomer population on-slope.

Lift usage statistics by customer demographic and/or customer profilemay be used to analyze the impact of upgrading lifts and/or building newlifts. For example, such information may help prioritize lift upgradesand/or additions based on the customer demographic/profile to beimpacted by the upgrade/addition.

Ski Patrol Coverage

Staff tracking module 604 may also provide visualization of ski patrolcoverage of the resort, thereby allowing areas that are over- orunder-patrolled to be determined. For example, by identifying staffmembers operating ski patrol duties, staff tracking module 604 maymonitor ski patrol members' use of lifts to determine the frequency withwhich trails are patrolled in comparison to the number of customerswithin the associated areas.

Grooming

Modeling tool 630 may be used to predict the effect of groomingpractices based upon customer demographics and profiles. Such modelingmay also allow grooming practices to be selected that target desiredcustomers.

Snow Making

Similarly, modeling tool 630 may predict the effects of snow making uponcustomer demographics and profiles, thereby allowing snowmakingpractices to be adjusted based upon a desired customer demographic andprofile effect.

Real-Time Lift Line Statistics

A lift wait analyzer 650 utilizes one or more algorithms to determinelift wait times. Where only a boarding zone of a ski lift is covered byRFID scanners (e.g., RFID scanners 104), lift wait times can only beestimated by lift wait analyzer 650. Lift wait analyzer 650 may trackrepeated access to the lift by customers to determine the accessfrequency of each returning customer. Based upon average and minimumtime intervals, lift wait analyzer 650 may determine if the lift linewait is increasing or decreasing.

As shown in FIG. 20, at least one RFID scanner 104(8) scans lift accessproduct 120 at a lift line entry area 2002 and generates a scan record128′. Scan record 128′ is processed by location event generator 110 togenerate a location event record 132′. The customer progresses throughlift line 2000 and lift access product 120 is scanned by RFID scanner104(9) as the customer enters a lift boarding area 2004 at the front oflift line 2000. RFID scanner 104(9) generates a scan record 128″ that isprocessed by location event generator 110 to generate a location eventrecord 132″. Lift wait analyzer 650 processes location event records132′ and 132″ (i.e., by identifying location event records for the samelift access product 120 at the same lift line 2000) and determines thetime spent by the customer progressing through lift line 2000 bycomparing the timestamps of these location event records. By averagingthe lift wait time of several customers progressing through lift line2000, an average lift line wait time may be determined.

Lift wait analyzer 650 may display real-time lift wait time informationon a lift wait time display 2006. In one example, lift wait time display2006 represents a web page generated by web portal 140 and may be viewedby resort operators. Lift wait time display 2006 may also represent adisplay of lift wait times on on-slope displays (e.g., kiosks) and/ormessage boards located at strategic on-slope locations (e.g., at liftdrop points). Thus, customers may use the lift wait time informationwhen planning trails to ski. In one example, lift wait times aredisplayed graphically on a resort map by using color symbolsrepresenting lifts, where red indicates long lift line wait, yellowindicates moderate lift line wait, and green indicates minor lift linewait.

FIG. 19 is a flowchart illustrating one exemplary process 1900 fordisplaying ski lift line wait times. Process 1900 is implemented withinlift wait analyzer 650, FIG. 6, for example. Steps 1902 through 1912form a loop that repeats for each lift of the ski resort. In step 1902,process 1900 selects each ski lift of the resort in turn. In step 1904,process 1900 selects location event records associated with the lift fora defined period up to the present. In one example of step 1904, liftwait analyzer 650 selects location event records 132 from locationdatabase 112 for the identified lift at lift line entry area 2002 and atlift boarding area 2004 for all customers. In step 1906, process 1900determines a time interval between entering the lift line and boardingthe lift for each customer. In one example of step 1906, lift waitanalyzer 650 first sorts the selected location event records bycustomer, thereby pairing location event records 132 for lift line entryarea 2002 and at lift boarding area 2004 for each customer. Lift waitanalyzer 650 then compares the time stamp of each location event recordof each pair to calculate the time spent by the customer progressingthrough the list line. In step 1908, process 1900 determines the averagewait time for the lift by averaging the determined time intervals forall customers utilizing the lift within the defined period of step 1904.In one example of step 1908, lift wait analyzer 650 sums the determinedtime intervals of step 1906 and divides by the number of determined timeintervals to generate an average wait time for the lift of step 1902. Instep 1910, process 1900 stores the average wait time in association withthe lift of step 1902. In one example of step 1910, lift wait analyzer650 stores the determined average wait time locally. In another exampleof step 1910, lift wait analyzer 650 stores the determined average waittime within a database in association with the lift selected in step1902.

Steps 1902 through 1912 repeat for each lift for which average lift waittime is determined. Where a ski lift does not have an RFID scanner 104at lift line entry area 2002, lift wait times may not be determined andthis lift is not processed in steps 1902 through 1912.

In step 1914, process 1900 displays a map of the resort indicatingaverage wait time for each lift of step 1902. In one example of step1914, lift wait analyzer 650 utilizes web portal 140 to generate a liftwait status page containing a resort map upon which color indicators aredisplayed, adjacent to each list hoarding area, to indicate lift linelengths. For example, a green circle may indicate minimum lift waittimes, a yellow square may indicate moderate lift wait times and a redtriangle may indicate extended lift wait times. This lift wait statuspage may be displayed upon on-slope kiosks (e.g., kiosk 528, FIG. 5) andother displays. A resort operator and/or manager may view the lift waitstatus page to monitor crowd behavior and to determine if additional orfewer lift operators are required at any particular ski lift.

Marketing

Information of customer profile database 612 may be used together withcustomer demographic information to determine targets for specializedadvertising and to create special offers. For example, advertisingand/or special offers may be used to target a certain customerdemographic and/or profile category for a certain day, where historicalinformation indicates that such customers utilize the resort lessfrequently on that day.

Predictive On-Mountain Population Modeling

Modeling tool 630 may utilize historical information from locationdatabase 112, customer profile database 612, and customer information116 to predict on-slope population by one or more of day, hour, zone,and customer profile. Such predictions may then be used to drivemarketing campaigns. Modeling tool 630 may use or incorporate liftprogression model 632 to predict on-slope crowd behavior and therebyidentify under-utilized areas of the resort. By analyzing customerprofile database 612, certain demographics and customer types may beidentified for additional marketing to increase attendance of thoseunder-utilized areas.

FIG. 16 is a flowchart illustrating one exemplary process 1600 formodeling crowd behavior. Process 1600 may be implemented within modelingtool 630, for example. In step 1602, process 1600 determines a customerprofile distribution to be modeled. In one example of step 1602, asnapshot of customers scanned and identified at the resort is determinedfrom location database 112 and a profile distribution is then determinedfor those customers based upon customer profile database 612. In step1604, process 1600 creates a model of the resort and populates it withthe determined customer profile distribution of step 1602. In oneexample of step 1604, modeling tool 630 creates a computer model 631 ofthe resort populated with customers identified in step 1602, where thesecustomers have modeled behavior based upon determined profiles of thosecustomers in customer profile database 612. Steps 1606 through 1618 ofprocess 1600 form a loop that operates to model customer behavior for aselected period or until a specified time.

In step 1608, process 1600 selects a period to model and/or a targettime. In one example of step 1608, a user inputs a target time for whichcrowd behavior is to be modeled. In another example of step 1608, aperiod is input for which modeling is to repeatedly occur. In step 1610,process 1600 adjusts model population based upon previously determinedpopulation trends. In one example of step 1610, population of model 631is adjusted based upon the modeled time of day and previously determinedpopulation changes (e.g., on-slope population decrease at lunch time).In step 1612, process 1600 operates the model for the period selected instep 1608. In one example of step 1612, modeling tool 630 operates model631 for the selected period, modeling behavior of customer populationbased upon modeled profile behavior. In step 1614, process 1600 analyzesthe model to determine crowd behavior. In one example of step 1614,modeling tool 630 analyzes model 631 to determine movements, lift linelengths, and population distribution after the modeled period. In step1616, process 1600 reports crowd behavior and predicted customerdistribution within the resort. In one example of step 1616, modelingtool 630 generates one or more reports and displays of the determinedcrowd behavior.

Steps 1606 through 1618 repeat for each desired period to be modeled.Thus, modeling tool 630 may generate a series of output predicting crowdbehavior over a desired period.

New Customer Capture

As described above, lift access products 120 may be divided into twoclasses: a first class lift access product (e.g., season passes) hasdescriptive information associated therewith, and a second class liftaccess product (e.g., free sell lift tickets) does not include suchassociated information. However, each lift access product includesunique identifier 122 which is encoded within the RFID tag and may beprinted in readable form on the lift access product.

The lift access products may also contain a URL of web portal 140.System 100 captures scan records 128 and location event records 132 forall lift access products, irrespective of class. However, to accessstatistics based upon these records, a customer must have an accountwith the resort that includes an affiliation to the identifier of thelift access product. For customers that are season pass holders, thataccount and affiliation may be created automatically by the resortand/or by the customer providing registration information online. Acustomer who has purchased and used a second class lift access product(i.e., a free sell lift ticket) may create an account with the resort byaccessing web portal 140, and may then enter the identifier 122 of thesecond class lift access product to associate it with the account.Having created the account and entered the affiliation to at least onelift access product, the customer may use the account to accessstatistical information determined by system 100 on the affiliated liftaccess product(s). The account also provides the resort with a way ofgathering new customer data and for building customer loyalty. Thecustomer may create the account at any time and may register the liftaccess product with the account at any time; customers may register thelift access product prior to and after use (i.e., after they havereturned from their ski vacation).

Real-Time Marketing

Marketing analyzer 670 may operate to process location database 112 forcurrent customer activity (e.g., activity for the current day) toprepare instant offers and discounts for customers currently utilizingthe ski resort. For example, marketing analyzer 670 may utilize customerprofiler module 610 to identify one or more customers having a certainactivity profile and target those customers, using on-slope messaging,for example, with discounts and suggested activities. For example,messages may be sent to active customers offering discounts in certainrestaurants at certain times. In another example, messages may be sentto certain customers suggesting alternative and less crowded trails.These customers may view their messages and offers at any on-slopekiosk. Such marketing may also attempt to distribute customers over theresort and avoid overcrowding in certain restaurants. For example, acertain group of customers identified by profile and demographic may beoffered discounts to utilize certain restaurants before anticipatedcrowds.

Customer Incentives

Each customer may readily avail themselves of statistical information ofexperiences received at the ski resort. For example, statistics web site534 may be access via on-slope kiosks, web browsers, cell phones, etc.Thus, customers are more likely to return to the resort to availthemselves of these statistics and facilities. In particular, based uponstored location event records 132 within location database 112, system100 may provide interactive trail maps that indicate a customer's liftutilization (with time stamps), and trails experiences. As describedabove, customers may interactively indicate trails experienced basedupon lift utilization. Statistics may be provided that indicate thenumber of days skied in a season (or other denoted period), the totalnumber of vertical feet skied, and the different resorts frequented.

In one embodiment, system 100 monitors each customer and awards thecustomer a category based upon the customer's activity level. Forexample, within system 100, customers may be associated with one of fourcustomer activity categories: platinum, gold, silver, and bronze. Eachcustomer may accumulate ‘experience points’ based upon their trackedactivities at one or more ski resorts. For example, a customer may earnexperience points by skiing different zones in a ski resort. Each skilift utilized by a customer may earn experience points, and additionalexperience points may be added for each different ski lift utilized at aresort. Each day skied at a resort may earn experience points.Experience points may also be added based upon the number of verticalfeet skied by the customer. The number of different resorts skied mayearn additional experience points. Based upon the number of experiencepoints earned by the customer, system 100 associated the customer withone of the four customer activity categories.

Each resort may then offer facilities to each customer based upon thecustomer's associated activity category. In one example, a gold categorycustomer may receive redemption rewards of a higher value than thosereceived by a silver customer.

Customers may also publish their information to social networking sites.For example, a customer may elect to have location and/or statisticalinformation published to their Facebook™ account, thereby allowing their‘friends’ to view their experiences.

Mountain Operations may utilize information within location database 112to generate a time-lapse view of the ski resort showing historical orprojected congestion in the ski lift network at the resort. Suchinformation may help the ski resort operators and/or management plan forchanges and additions at the resort.

Changes may be made in the above methods and systems without departingfrom the scope hereof. It should thus be noted that the matter containedin the above description or shown in the accompanying drawings should beinterpreted as illustrative and not in a limiting sense. The followingclaims are intended to cover all generic and specific features describedherein, as well as all statements of the scope of the present method andsystem, which, as a matter of language, might be said to falltherebetween.

What is claimed is:
 1. A method for monitoring skier behavior,comprising: reading an identifier from a lift access product when thelift access product is within a lift line entry area; generating a firstscan record containing the identifier, location information of the liftline entry area, and a time stamp; reading the identifier from the liftaccess product when the lift access product is within a boarding area;generating a second scan record containing the identifier, locationinformation of the boarding area, and a second time stamp; processingthe first and second scan records to determine a lift wait time.
 2. Themethod of claim 1, wherein the step of processing the first or secondscan records further comprises determining a profile of a skier usingthe lift access product.
 3. The method of claim 2, wherein the step ofprocessing the first or second scan records comprises determining skilift progression of the skier.
 4. The method of claim 2, wherein theprofile of the skier is accessed using a user interface deviceconfigured to access the lift access product and to display personalstatistics derived from location event records for that skier.
 5. Themethod of claim 4, wherein the user interface device is configured todisplay a location of each of one or more persons that have formed aparty with the skier.
 6. The method of claim 5, wherein the location ofeach person in the party includes a particular lift that each person inthe party is currently riding or a time and ski lift last ridden by eachperson in the party.
 7. The method of claim 4, wherein the userinterface device is a kiosk.
 8. The method of claim 7, wherein the kioskis configured to automatically log in the skier using the lift accessproduct.
 9. The method of claim 4, wherein the user interface device isa cell phone.
 10. The method of claim 5, wherein the user interfacedevice is configured to add profiles of persons to the party using liftaccess products for each of the additional persons.
 11. The method ofclaim 1, wherein an RFID scanner is used to read the lift accessproduct.
 12. A system for monitoring skier behavior, comprising: a firstscanner, wherein the first scanner reads an identifier from a liftaccess product when the lift access product is within a lift line entryarea; a record generator, wherein the record generator generates a firstscan record containing the identifier, location information of the liftline entry area, and a time stamp; a second scanner, wherein the secondscanner reads the identifier from the lift access product when the liftaccess product is within a boarding area, and wherein the recordgenerator generates a second scan record containing the identifier,location information of the boarding area, and a second time stamp; alift wait determiner, wherein the lift wait determiner processes thefirst and second scan records and determines a lift wait time.
 13. Thesystem of claim 12, further comprising a profile generator, wherein theprofile generator processes the first or second scan records todetermine a profile of a skier.
 14. The system of claim 13, wherein theprofile of the skier includes ski lift progression of the skier.
 15. Thesystem of claim 13, wherein the profile of the skier is accessed using auser interface device configured to access the lift access product andto display personal statistics derived from location event records forthat skier.
 16. The system of claim 15, wherein the user interfacedevice is configured to display a location of each of one or morepersons that have formed a party with the skier.
 17. The system of claim16, wherein the location of each person in the party includes aparticular lift that each person in the party is currently riding or atime and ski lift last ridden by each person in the party.
 18. Thesystem of claim 15, wherein the user interface device is a kiosk. 19.The system of claim 18, wherein the kiosk is configured to automaticallylog in the skier using the lift access product.
 20. The system of claim15, wherein the user interface device is a cell phone.
 21. The system ofclaim 12, wherein the at least one scanner is an RFID scanner.